Case Pipeline Prototype | ODPP Digitisation Pack

Office of the Director of Public Prosecutions

Case Pipeline & Complaints Console

{{ me.name }} {{ me.title }} · {{ me.scope }}

How to read this prototype This is a working demonstration, not a report. Sign in as any of the eight accounts below to view the system through that officer's permissions: each account sees different stations, different records and different complaints, and an attempt to open a case outside an account's scope is refused and recorded. Within the console, the ten numbered records across the top are the paper chain from station diary to judgement; selecting one opens its folder of documents, its timing, and the facility to lodge a complaint at that stage. An introduction to the wider pack is available in the Digitisation Pack.

Restricted system Case pipeline detail is not public. Assigned officers sign in and follow the file on behalf of the complainant. Members of the public get a complaints tracker and nothing more — no officer names, no case narrative, no file location, no stage detail. Choose a door.

Eight accounts — pick one to see the console through that officer's permissions

Track your complaint Enter the reference and the six-digit PIN on your slip. Try CMP/NAK/2026/00412 with any six digits.

Complaint reference Six-digit PIN

What the public is never shown

· The name, rank or force number of any investigating officer or state attorney · The case narrative, statements, exhibits or any document in the jacket · Where the physical file is, which registry holds it, or who is carrying it · Which stage of the ten-record chain the case has reached · Whether a conduct complaint exists against anyone · Any other person's complaint, however similar

A status line and a next-step sentence is the whole public disclosure. Everything else in this system requires a named account, a role, and an entry in the audit log.

Station {{ station.stationName }} {{ station.division }}

Complainant {{ station.complainant }} {{ station.complainantMeta }}

Accused & offence {{ station.accused }} {{ station.offence }}

Four ledgers, one case

Total {{ station.totalDays }} days, SD to judgement

Bottleneck {{ station.worstDays }} {{ station.worstLabel }}

Judgement {{ station.outcome }} {{ station.outcomeDate }}

Complaints on this case

No complaint lodged on this file. Open any stage and use the two buttons at the foot of the record.

The chain — ten records, three institutions Click any record to read what it captures, then query the stage or complain about the officer.

within benchmark slow bottleneck

Phase 1 · Police station — records 01–04

Phase 2–3 · ODPP — records 05–08

Phase 4 · Court

Fields captured on this record

Folder — record {{ stage.num }} · {{ folderSummary.count }} documents {{ folderSummary.verdict }}

Authored by {{ d.author }} Dated {{ d.date }}

Systemic function — {{ stage.function }}

What went wrong here — {{ stage.risk }}

Timing on this file

Dated {{ stage.date }}

Time in stage {{ stage.dwellText }}

Officer accountable at this stage {{ officerLine }} {{ officerMetaLine }}

This record carries {{ stageFlagCount }} registry flag — visible to every officer who opens the file.

Registry action · record {{ stage.num }}

Move the physical file to Officer or courier taking custody

Reason for the flag

Note for the register

Complaint at this stage — lodged on behalf of the complainant

This account cannot lodge or record complaints. Complaints are taken by the registry, the Inspectorate or the Head of Complaints — never by the officer whose work is being questioned.

{{ form.title }} Against record {{ form.stageNum }} · {{ form.stageShort }}

{{ form.categoryLabel }} What happened, in your own words

Your name Phone

Complaint lodged — keep this slip

Your reference {{ receipt.reference }}

PIN — shown once {{ receipt.pin }}

Internal file {{ receipt.iaf }} opened in the isolated disciplinary registry. {{ receipt.officer }} has no read permission on this record and will not be told who lodged it.

Registries and sub-registries — where the file physically is

The 18 regional sub-registries — highlighted is the one holding this file

Physical hops{{ movementSummary.hops }}separate custody transfers

Blind legs{{ movementSummary.blindCount }}no return receipt to the sender

Days unwitnessed{{ movementSummary.blindDays }}nobody could locate the file

Signatures{{ movementSummary.handovers }}hands the jacket passed through

{{ m.from }} → {{ m.to }} {{ m.tierLabel }}

Out {{ m.out }} In {{ m.arr }} Carried by {{ m.courier }} {{ m.daysLabel }} in transit {{ m.trackedLabel }}

Officer analytics — where the pipeline is losing time {{ analytics.caption }}

Where the days go — share of elapsed time by institution

Complaints lodged — type and target

Days spent in each of the ten records Red bar is the bottleneck. Dotted line is the 14-day service benchmark.

Cumulative days elapsed, all three stations

Complaints register — scoped to your account Type A rows show a sealed narrative: the register knows a file exists, not what it says. That is the isolation rule from the process document.

Reference

Type

Against record

Substance

Routing

Status

Registry flags raised on this file

{{ f.reason }} {{ f.where }} · raised by {{ f.by }} {{ f.note }}

Audit trail — this session Every sign-in, case opened, movement, flag and refused access is written. In production this table is append-only and readable only by the DPP and the Inspectorate — reads of a conduct file are logged the same way.

{{ a.stamp }} {{ a.action }} {{ a.detail }} — {{ a.who }}, {{ a.role }}

Built by